How do I get `gem` working again after upgrading to rubygems 1.8.x?

Had this problem with gems 1. {7..8} Here's our production stack: MRI 1.9.2 and JRuby 1.6.1 RVM 1.6.5 Gems 1.6.2 Stay away from upgrading gems itself, or shit may break. I know how tempting it is to use bleeding edge, but it's more like profusely hemorrhaging all over the O.R.Walls If you must: Current user only (more common): gem install rubygems-update -v 1.6.2 && update_rubygems System-wide (caution): sudo gem install rubygems-update -v 1.6.2 && sudo update_rubygems If using RVM, be sure to rvm gemset global first Usual caveats apply such as backup your data, gemsets, apps and don't try this in production.

:).

Had this problem with gems 1. {7..8}. *.

Here's our production stack: MRI 1.9.2 and JRuby 1.6.1 RVM 1.6.5 Gems 1.6.2 Stay away from upgrading gems itself, or shit may break. I know how tempting it is to use bleeding edge, but it's more like profusely hemorrhaging all over the O.R. Walls. If you must: Current user only (more common): gem install rubygems-update -v 1.6.2 && update_rubygems System-wide (caution): sudo gem install rubygems-update -v 1.6.2 && sudo update_rubygems If using RVM, be sure to rvm gemset global first.

Usual caveats apply such as backup your data, gemsets, apps and don't try this in production. :).

Thanks... I downgraded to 1.6.2, and life is better now. I used this command: "gem update --system 1.6.2" – llimllib May 10 at 3:24 Great analogy there. :) FWIW, I gave upgrading a try using the rubygems-update method you suggested, and that fails too--the nice thing is, though, that I'm left with a usable gem command, unlike with the other method.

I guess I'm stuck on 1.6.2 for now... – turboladen May 11 at 2:22 One of my machines is running 1.3.7, and it works perfectly. Thanks a lot for figuring out which version works. – Jamie Penney May 11 at 2:34 FWIW, things seem pretty stable up till 1.6.2.

I've had pretty good success with 1.7.2, but people at work haven't shared that success and are still holding at 1.6.2. – turboladen May 12 at 23:04 Downgrading is good advice, at least for now. See this bug report for more details... and please leave a supportive comment if you want my patch to be accepted.Rubyforge.Org/tracker/… – Alex Chaffee May 13 at 22:01.

It's not tied to RVM, as I'm running the same version. It's not Ruby 1.9.2 either, again because I'm running the same version. Gem uninstall ... returning errors isn't normal.

I've done the upgrade on several machines running RVM and 1.9.2 and gem itself continued running correctly. And, yes, I saw the deprecated warnings. Is it possibly you ran gem update using sudo?

That would probably break it since you're running under RVM, and sudo is a major no-no.

Interesting. I figured it wasn't normal, as I didn't find anyone else saying anything similar. I'm sure I didn't run using sudo--I've used RVM for so long that I'm totally out of that habit.

:) – turboladen May 11 at 1:37.

Well... I encountered the same error as you after updating rubygems and doing gem pristine --all --no-extensions. I, on the other hand, didn't understand the major no-no about doing my gem installs and updates using sudo, so I have a whole other mess to clean up. However, this is how I got back to a working installation: I updated rvm by doing a fresh install: beginrescueend.com/rvm/install/ I encountered some other permissions issues with this step due to my no-no sudo'ing ways, but got past it.

I did have to open a new terminal session for the changes to work. Then, $ rvm rubygems current as described here: beginrescueend.com/rubies/rubygems/ This installed version 1.6.2. So far, I seem to have a working gem command again, and my deprecation warnings are gone.

Hope it helps.

It's not tied to RVM, as I'm running the same version. It's not Ruby 1.9.2 either, again because I'm running the same version.

I cant really gove you an answer,but what I can give you is a way to a solution, that is you have to find the anglde that you relate to or peaks your interest. A good paper is one that people get drawn into because it reaches them ln some way.As for me WW11 to me, I think of the holocaust and the effect it had on the survivors, their families and those who stood by and did nothing until it was too late.